Repository navigation
Add a repin command - #2
Merged
Merged
Conversation
Repinning a content repo onto a new kit tag had two traps, and the v1.2.0 rollout hit the first one: `npm install` alone does not repin. package-lock.json records the resolved COMMIT of the previous tag, so npm honours the lock and keeps the old kit even though package.json names a new tag. The install prints "changed 1 package" and exits 0. One repo got a commit claiming to repin while still running the old kit; it was caught only by running `workshop-kit --version` by hand. Second, a release that touches agents/base.md moves the AGENTS.md fence hash, so a repin that does not regenerate leaves `agents check` failing in a repo that otherwise looks fine. `workshop-kit repin <tag>` closes both: it forces re-resolution with the explicit spec form, then asserts the installed version actually matches the tag, regenerates AGENTS.md as part of the same operation, and runs agents check, validate-config, typecheck and build before reporting success. It refuses a tag that is not on the remote before touching package.json, so a typo cannot leave the repo half-modified. Verified end to end on maestro-workshop: a real downgrade to v1.1.0 (fence tracked back to 199aad91) and back up to v1.2.0 (fence 29a89812) returned the working tree to exactly its committed state. Error paths checked too — missing tag, unknown tag, and running outside a content repo. The README now documents the release-and-repin flow, including that Dependabot does not and will not propose these bumps for a github: tag dependency. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repinning a content repo onto a new kit tag had two traps. The v1.2.0 rollout hit the first one.
The silent no-op
npm installalone does not repin.package-lock.jsonrecords the resolved commit of the previous tag, so npm honours the lock and keeps the old kit even thoughpackage.jsonnames a new tag. The install prints "changed 1 package" and exits 0.During the v1.2.0 rollout one repo got a commit claiming to repin while still running 1.0.1. It was caught only by running
workshop-kit --versionby hand. Nothing in the pipeline would have failed.The fence hash
A release that touches
agents/base.mdmoves theAGENTS.mdfence hash, so a repin that does not regenerate leavesagents checkfailing in a repo that otherwise looks fine.What the command does
workshop-kit repin <tag>:package.json, so a typo cannot leave the repo half-modified.npm install <pkg>@<spec>form.AGENTS.mdas part of the same operation, not as a follow-up.agents check,validate-config,typecheckandbuildbefore reporting success.Verification
Tested with a real version change, not a dry run. On
maestro-workshop: downgraded to v1.1.0 and back to v1.2.0.29a89812→199aad91→29a89812.Error paths: missing tag, unknown tag, and running outside a content repo all fail cleanly with a usable message.
Also
The README now documents the release-and-repin flow, including that Dependabot does not and will not propose these bumps for a
github:tag dependency — verified in practice, and the dead group is being removed from the four content repos.Note the bootstrap: v1.2.0 does not have this command, so the first repin onto v1.3.0 runs from a kit checkout. Every repin after that works via
npx workshop-kit repin <tag>.🤖 Generated with Claude Code